An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hi everyone, I’m looking for guidance regarding an unusually long App Review delay. My first iOS app, EmpowerFI, has been in “Waiting for Review” for almost 30 days. In two days, it will reach a full month without moving to “In Review.” During this period, I have contacted Apple Developer Support several times. After my initial contact, Apple submitted an expedited review request as a one-time exception for my app. However, the status did not change. I contacted support again and received the following response: “We have confirmed that your app review is proceeding normally, and there is no further action you need to take.” I have followed up multiple times since then, explaining that I am not asking Apple to guarantee a review or approval date. I am simply trying to understand why this particular submission has remained in “Waiting for Review” for almost a month. Unfortunately, I continue to receive essentially the same standard response. There are no pending actions visible in App Store Connect, and Apple Support has explicitly confirmed that there is nothing further required from me. I fully understand that review times vary and that some apps may require additional scrutiny. However, almost 30 days without even moving from “Waiting for Review” to “In Review” seems exceptionally long, particularly after an expedited review request was submitted. I also know developers who submitted apps during this period and received a review response within approximately two days, so I am trying to understand whether there could be something specific affecting my submission. Has anyone recently experienced a similar delay with a first app submission? More importantly, is there any other appropriate escalation path when Developer Support confirms that everything is normal but the app remains in “Waiting for Review” for almost a month? I am not looking to bypass App Review or request guaranteed approval. I would simply like someone to investigate whether there is an issue affecting this submission or explain why it has remained in the queue for such an exceptional amount of time. Any guidance from Apple staff or developers who have experienced this recently would be greatly appreciated. Thank you,

Hi, I’m running into a persistent issue in App Store Connect related to TestFlight and app reviews, and I’m hoping someone has seen this before. Around two weeks ago, I started getting the following error when trying to create external TestFlight builds: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING Since then: I cannot create any external TestFlight tests Internal TestFlight builds appear, but cannot be downloaded (“The requested app is not available or doesn’t exist”) My apps do not progress properly through review One app got stuck in “In Review” for ~10 days; I eventually withdrew it and resubmitted it At this point, I cannot update two existing apps, and I can’t start testing a new app at all Important details: This is an individual developer account I am the Account Holder All contracts appear active and valid The issue affects multiple apps, not just one Nothing changed on my side (no contract updates, no account changes) before this started happening. I’ve already reached out to Apple Developer Support multiple times, but unfortunately haven’t received any response so far, which makes it unclear how to proceed. Has anyone experienced this issue or found a resolution? Any insight would be greatly appreciated. Thanks!

Hi, My macOS app, Notiz Me, received a "Guideline 2.1 - Information Needed" message on September 3, 2026. This was flagged as a new developer account with limited App Review history, and I was asked to provide additional information about the app. I replied the next day (September 4) in the Resolution Center with detailed answers to all six requested items, plus a screen recording demonstrating the app's core functionality. I also added the same information to the App Review Information Notes field, as instructed in Apple's message. It has now been over a week with no response. I sent a follow-up message today, but there has been no update in App Store Connect since my original reply on September 4. Submission ID: 1301bf30-de8f-419e-9fe1-75edd8b6884b App: Notiz Me (macOS) Bundle ID: com.prakashyuvaraj.notizme Could someone please help check the status of this submission, or surface it to the App Review team? Happy to provide any additional information needed. Thank you.

Dear App Review Team, I am writing to respectfully request an update on the review status of our first-time app submission, which appears to be stalled in the queue. Here are the specific details of the submission: App Name and Version: Bingo Rewards! (Version 15.54.34) App ID: 6793050466 Bundle ID: com.apperfun.bingorewards Submission Date: August 31st Current Status: The build remains strictly on "Waiting for Review" and has not transitioned to "In Review." Previous Actions: This is our first app submission. The initial build was previously rejected, after which we thoroughly fixed and addressed all noted issues before resubmitting this current version on August 31st. Given that the app has been in the "Waiting for Review" status for over a week following our resubmission, we wanted to ensure there are no outstanding requirements or technical blockers on our end preventing the review from moving forward. Please let us know if you need any additional information or clarifications to assist with the evaluation of this build. Thank you for your time and assistance.

Six people. Four years. One app on the App Store since 2022 — completely free, no payments, no in-app purchases, no subscriptions. Sixteen released versions. Real users. In May 2026 Apple flagged our developer account for termination. The stated reason: "dishonest or fraudulent activity" under Section 3.2(f) and Guideline 5.6.2. That was the entire explanation. Not which app. Not which metadata. Not which action. Not which build. Nothing. We asked. Six times over three months. We offered to revert our branding, remove any feature they named, re-verify every piece of company information. We asked, plainly: tell us what we did wrong and we will fix it today. The App Review Board answered twice — the same template both times. "A pattern of manipulative or misleading behavior," followed by a generic list of things such behavior "can include, but is not limited to." Not one specific. Not once. In four months. What that looks like from our side: — Three apps pulled from the App Store overnight — Earnings frozen — App transfers disabled — Three months of "we are experiencing a higher case volume" — A final decision that repeats the original accusation word for word — A reinstatement petition filed on 27 August. Thirteen days. No response. No phone call. No human being. No specifics. No appeal beyond a web form that answers with a template. Apple's own Guideline 5.6.2 reads: "Providing verifiable information to Apple and customers is critical to customer trust." Verifiable. Apple demands verifiable information from developers, then terminates them on grounds it refuses to specify, and calls that a review process. Six people lost their work. Their families lost their income. Four years of building on a platform that can end your business overnight and owes you no explanation. If you build on the App Store, understand what you are building on. If you have been through this — reply here. I want to know how many of us there are.

Hello, We have submitted our app on August 10th, and still "Waiting for Review" for over 20 days. Can anyone help us resolve this issue?

I am trying to add testers to External Tester groups for a couple of our iOS apps and after adding them it shows "No Builds Available". This is despite the app being available to that External Tester group with other people having already installed the latest version of the app which is "Available" and not expired. Can someone please fix this? It is so frustrating the number of times I try and release apps to TestFlight and there's some issue blocking me, completely out of my control and I have to rely on someone at Apple fixing something on this terrible AppStoreConnect system.

Hi everyone, I’m looking for some clarification regarding Privacy Manifest requirements (PrivacyInfo.xcprivacy) after resolving a validation issue on my latest submission. In my previous build, I ran into an issue related to NSPrivacyTracking and NSPrivacyTrackingDomains. I updated the manifest to ensure NSPrivacyTracking is set to <true/> alongside our App Tracking Transparency (ATT) prompt, and restricted NSPrivacyTrackingDomains strictly to the required ad service endpoints (googleadservices.com, googlesyndication.com, doubleclick.net, etc.), removing any broad domains. I have just submitted the corrected build: • App Name: Girls vs Boys Tapping • Version: 1.1.2 • Build: 112 • Apple ID: 6809284204 • Status: Waiting for Review Since this is my first time submitting with the updated privacy manifest format after resolving that error, my question is: Once the build enters the review queue with these specific tracking domains and ATT configured, does App Review require any additional documentation in the review notes regarding the ad network tracking domains, or is the .xcprivacy file inside the bundle sufficient for automated validation and review? Just want to make sure everything is 100% in order so there are no unexpected hold-ups while it's in the queue. Thanks in advance for any insights!

Hello, I’m posting here to ask for guidance and to see if anyone has experienced a similar situation. More than 30 days ago, I submitted an appeal to the App Review Board after receiving a Pending Termination Notice for my Apple Developer Program account. However, I have not received any response or update since submitting the appeal. In the notice, Apple mentioned that my account was associated with “dishonest or fraudulent activity” related to app submissions. I want to clarify that I did not intentionally attempt to bypass the App Review process. The only change I made around that time was editing some app metadata (subtitle keywords) while trying to optimize my Apple Search Ads campaign. Looking back, I now understand that some of those keywords may have been interpreted as referencing content that Apple considers inappropriate for the App Store. After realizing this might have caused an issue, I immediately: Canceled the latest app submission that contained those metadata changes Explained the situation clearly in my appeal to the App Review Board Confirmed that I would avoid using similar metadata in the future Despite providing this explanation in my appeal, I have not received any reply or update for over a month, so I’m unsure about the current status of the appeal. If anyone here has gone through a similar process, could you share: How long it took to receive a response from the App Review Board? Whether it’s normal for appeals to take this long? Also, if any Apple staff happens to see this post, I would sincerely appreciate any guidance on whether my appeal is still under review or if there is anything further I should provide. Thank you very much for your time and help.

Hello everyone, I’m looking for advice from developers who have experienced a similar App Store rejection under Guideline 5.6 – Developer Code of Conduct. My app is called Al-Saqar. It is a specialized marketplace and auction platform for falconry enthusiasts. The app includes: Falcon listings and physical product sales Falcon food and accessories Real-world falcon auctions Live auction viewing and bidding Falcon farms and clinics directory Search and filtering User accounts and account deletion All products and auction items are physical goods. There are no digital goods or subscriptions being sold through the app. For auctions, users can view the auction and watch the bids. To participate, they need to complete identity verification and pay a security deposit. The deposit and final payment are handled outside the app through our support team and bank transfer because these are real-world, high-value transactions. Apple rejected the app under Guideline 5.6 with the following message: “We've identified a pattern of unusual behavior with the app that is commonly associated with fraudulent activity. Specifically, the app contains features that appear to have been intentionally hidden during the review process.” The problem is that Apple did not identify which feature, screen, account state, or behavior they believe was hidden. There are no hidden features intended to be shown only to normal users. The functionality available to users is the same functionality available during review. I have already tried to clarify this with Apple and provided additional information and a screen recording demonstrating the functionality on a real device. I have also submitted an App Review Board appeal, but I am still trying to understand what could be triggering this rejection. Another thing I noticed is that the review appears to have happened extremely quickly, which makes me wonder whether some automated detection or account/runtime behavior could be involved. I obviously cannot confirm that this is the case. I have been trying to publish this app since August 18, 2026, and I have now reached a point where I don't know what I should actually change because Apple has not identified the specific issue. Has anyone experienced this exact Guideline 5.6 rejection, especially the wording about: “features that appear to have been intentionally hidden during the review process” and successfully resolved it? If so, I would really appreciate knowing: What was actually causing the rejection? Did Apple eventually identify the specific feature or behavior? Was it related to remote configuration, server-side logic, feature flags, account states, device/region checks, dynamic content, or third-party SDKs? Did contacting Apple Support or requesting an App Review appointment help? Did you need to submit an appeal, or did a new build eventually resolve the issue? I am not looking to bypass App Review. I simply want to understand what Apple is detecting so I can fix the actual problem instead of making random changes and repeatedly submitting builds. Any experience or advice from developers who have gone through the same situation would be greatly appreciated. Thank you.

Hello App Review team, Could you help investigate a possible false-positive similarity classification across my apps, or advise which channel can examine these review events together? My concern is based on the recorded timing, the different purposes of these apps, and a previously approved bowling app whose update was rejected twice under 4.3(a), then subsequently approved. Striker: Bowling Coach and Fotij Striker is a bowling coaching app. Fotij is a color analysis and personal styling app. These were the two apps rejected together in the August events below. App Store Connect records: August 21, 2026: Striker 1.0 was approved and became Ready for Distribution. August 28 at 00:23: Striker’s 1.01 update and Fotij 0.1.0 both entered In Review and were marked Rejected within that same displayed minute. August 28 at 18:22: Both apps again entered In Review and were marked Rejected within the same displayed minute. Both rejection messages for each app cited Guideline 4.3(a). Striker 1.01 was submitted again. On September 5, it entered review at 14:16 and became Ready for Distribution at 14:19. The completed submission shows 1.01, build 4, Approved. The later approval was for the same marketing version, 1.01. Whether the binary or metadata differed across individual attempts should be checked against Apple’s submission records. Camera1X: a separate, later occurrence of the same pattern Camera1X is a native photography app combining depth capture, interactive 2.5D parallax and 3D Motion export, guided Moon/Stars/Moon + Landscape capture, and private on-device spatial reconstruction. Its review history shows: August 6: In Review at 09:21, Rejected at 11:25 — approximately two hours. September 7: In Review at 17:25, Rejected at 22:47 — approximately five hours. This review returned a specific Guideline 2.1(b) purchase issue, which we addressed. September 9: In Review at 01:34, Rejected under 4.3(a) at 01:34. Fotij also entered In Review and was rejected under 4.3(a) at 01:34 that day. The two replies already sent for Camera1X In my first reply, I disputed the 4.3(a) finding and explained Camera1X’s functional capture and processing workflows. I raised the concern that similarity screening might be incorrectly grouping independent apps. I requested a manual review and identification of the specific binary components, assets, metadata, or app concept behind the finding, including a comparison app where possible. In my second reply, I clarified that Camera1X had previously undergone two reviews lasting hours, while the latest rapid rejection coincided with separate apps receiving the same finding. I again requested an individual assessment of each app’s actual functionality and a concrete explanation of the alleged overlap. I also explained that I would resubmit Camera1X first and wait for its review to conclude before resubmitting the other new apps. Camera1X 1.0.0 (6) is currently Waiting for Review. All times above are displayed in App Store Connect in UTC+03:00. The history has minute precision, so matching timestamps alone do not prove that a decision was automated. However, the repeated timing across apps with different purposes, together with Striker’s subsequent approval, raises a concern that I would appreciate Apple investigating. Could App Review staff: Compare these events and check whether an erroneous similarity association could explain the pattern? Identify the concrete overlap behind the 4.3(a) findings so I can address a specific concern? Advise how to provide the full review histories, submission IDs, and both Camera1X replies privately, and which support or appeal channel should track the investigation? Thank you, Aziz Saba

Hi, our new app Amisoria (App ID 6805385809, Submission ID 95e40745-299b-4467-b9f6-8dd5ca907b02) was submitted Aug 29. On Aug 30 we received a Guideline 2.1 "Information Needed" message; we replied Aug 31 with all eight requested items including a screen recording, and followed up on Sep 3. We also opened Developer Support case 102955409950 on Sep 7. There has been no response of any kind since Aug 30. Could someone from App Review please take a look? The app is a client for a self-hosted AI gateway; a built-in demo mode lets reviewers test it without any server. Thank you.

Hello, Our first App Store release, 2ndBook 1.0.0 (build 251), has remained in “Waiting for Review” since August 29, 2026 and has never moved to “In Review”. App: 2ndBook Version: 1.0.0 Build: 251 Platform: iOS / iPadOS Bundle ID: kz.stybaye.secondbook Submitted: August 29, 2026 Current status: Waiting for Review The binary has been successfully processed and there are no outstanding actions or messages shown in App Store Connect. We have already contacted Apple Developer Support regarding the review status and an official support case has been opened. Could someone from the Apple App Review team please verify whether this submission is correctly present in the review queue, or whether it may be affected by an internal routing or processing issue? We do not want to withdraw and resubmit the application, because we would prefer to preserve the existing submission and its current queue position. Please let us know if any additional information or action is required from our side. Thank you.

Hello, our app Rezzy Baby (App ID 6807484857, build 1.0.0 (4)) was submitted on Sept 2 and received a Guideline 2.1 Information Needed request on Sept 3. We answered all six questions the same day at 19:43, attached a 5-minute screen recording, and put the same details in the App Review Information notes. Demo accounts and the backend have been online the whole time. There has been no reply since Sept 3, and the status still shows Rejected with Resubmit disabled. We sent a follow-up in the message thread today. Is there anything else App Review needs from us to continue? Thank you.

I'm an iOS developer in India, not yet enrolled, and I want to confirm my distribution architecture before I incorporate and pick an account type. What I'm building: patient-facing appointment and clinic-management apps for independent single-doctor clinics. One shared codebase; branding, clinic details, and backend configuration differ per clinic. The clinics will not enrol in their own Apple Developer Program accounts. I would register a company and enrol as an Organization, that company provides the software platform, while the medical services are provided by the individual clinics. Under 4.2.6 and 4.3(a), is a separately branded app per clinic viable from a single Organization account? My reading is no, and that the aggregated or "picker" model, one app where patients select their clinic, is the intended path. Is that correct? Under 5.1.1(ix), for that aggregated app, is my company an acceptable seller given that the medical services themselves are delivered by the clinics? Or does Apple expect each clinic to be the seller? If separately branded per-clinic apps are only possible when each clinic enrols in its own account, can I be added to their teams and submit on their behalf, or must the clinic itself submit? Are there additional review requirements for apps tied to medical practices, clinic licensure documentation, proof of authorisation to publish on their behalf, or a regulated medical device declaration, where the app only handles appointments, records, and clinic administration rather than diagnosis or measurement? Developer Support case 20000147392668 (they directed me here for the guideline questions).

Dear App Review Team, Our app No.IA (Apple ID: 6768742372) has been in "Waiting for Review" since July 20, 2026. This is version 3.1, resubmitted after the App Review Board cleared Guidelines 2.3.1 and 3.2.1 (Appeal Ticket APL509468). All Guideline 1.1 concerns have been addressed: metadata rewritten, in-app labels updated, screenshots replaced. We have tried: Resolution Center reply, expedited review request, phone call to Developer Support (Case 102912803305). All responses have been generic with no timeline. This app has been in review processes since May 19, 2026 — over 75 days. Any assistance would be greatly appreciated.

Hello, since July 31st, our app has been stuck in the waiting for review state for a long period of time. We have already taken some actions. July 31: first submission. August 10: after waiting for over a week, we assumed there was a problem with the review queue -> cancel and resubmit. We attempted to submit an expedited request, but there was an issue with Apple service. It keeps saying "Sorry, we didn't receive your request." August 13: request a call with the Support Team. There was a guy named Tony who answered. Unfortunately, even Apple's staff is unable to access their internal system, as he told us that, and "he don't know why"? August 14: request a call again. Apple staff - Andy took up the phone and said he could not do anything about this situation and said... We just have to wait. August 25: rejected the build, upgraded the version, and submitted once more. We're hoping that this build will get out of the stucked queue... Side notes: Attempted to submit another expedited request were unsuccessful, the problem remained, tried several times. Made an appointment for a App Review team. But even the registration is still pending. Does anyone here have suggestions or solutions for this situation? This is the first time we've encountered this situation, and it's quite strange. Isn't that a side effect of the August 8th maintenance?

Hello App Review Team, I'm writing to request an urgent status update and expedited review for our app, BlockP (App ID: 6705133649). Our most recent update has been in review for over 13 days, well beyond Apple's typical review window of 24–48 hours (and even beyond the outer bound of 7 days we've referenced in prior communications). This delay is materially affecting our business: A critical bug fix /feature our users are waiting on is stuck in this build users are affected by the issue this update resolves Details: App name: BlockP App ID: 6705133649 Build/version currently in review: 3.0.2 Date submitted: 2 sep 2026 Days in review: 13+ Could you please: Confirm the current status of this build and whether it requires any action from us Advise whether anything in this submission is causing an extended manual review Expedite this review given the above impact We're happy to provide any additional information needed. Thank you for your help resolving this quickly. Best regards,

Hello, Apple! I accidentally uploaded a version with a critical bug. Apple, please accept my new version—it’s urgent. Thank you very much.

My game was submitted for app review for few round, every time they rejected and i resolve the issue, but latest they reject as Guideline 4.3(a) - Design - Spam and dont have response more than 1 week, I am confusing, early stage was Code of developer (showing what my game have with recording),later follow by some bug fix, then design copy-cat ( the game is totally written by me), but then i asked many round please pin point which part. End up they reject with "Guideline 4.3(a) - Design - Spam" and i replied with full list of unique feature my game have and explaination on some feature where mostly every game have it such as stamina regen, ranking, gacha. Please help, my game was on google play for 1 week plus, some players of follower was asking for ios. google play link : https://play.google.com/store/apps/details?id=com.bubluestudio.beyondgod